Subject: DRAFT notes for Sessions 2&3

From: "Deirdre Kostick" <dck2@ginsu10>
Date: Mon, 17 Oct 94 12:08:22 -0400

Folks --

Attached are DRAFT notes
from the 2 & 3rd sessions
of the DLSw MIB meetings
at the AIW6 (last week in Raleigh)

Please check for accuracy, etc.

Pls send comments by Weds 5pm

Thanks,

Deirdre
[email-masked]
***********************************************

DRAFT Minutes of SNA DLSw MIB Sessions 2 & 3 - AIW6
=========================================

ACTION ITEMS & SCHEDULE
-----------------------

1) 10/21/94 -- Post input/comments from AIW6 meetings
   to [email-masked]
   who: Peter Gayek, Alan Sciacca, Paul Brittain
   ( See Item 5 for specifics.)

2) 11/1/94 --- Post 1st rough cut draft mib based on
   proposal, plus changes discussed during the meeting,
   plus input received by 10/21/94 on the mailing list
   who: David Chen

3) 11/8/94 --- Conference call to finish walkthrough of
   proposal & review 11/1/94 draft

   PLEASE NOTIFY DEIRDRE KOSTICK at [email-masked]
   if you want to be added to the list of participants 
   for this call**************************************

4) 11/1/94 --- Request/schedule BOF at IETF meeting 12/5
   in December to accelerate DLSw MIB work activities
   who: Deirdre Kostick

5) 10/21/94 --- Follow-up Action Items 

   + dlswResourceApply Object --- Need to add object/text
     indicating when/how Manager-requested changes
     (i.e., SetRequests) are applied by an Agent. 
     Issues discussed include multiple managers, what
     happens when a requested change is not successfully
     applied by the Agent. (Al)

   + Transport Type Objects -- Need to define objects/text 
     for information related to support of different 
     transport types & update the current proposal (Peter)

   + "Global" control Objects -- Need to define objects/text
     for global parameters such as window-size, keep-alives
     (Al)
  
   + Caution on using counter information for Accounting --
     Add text recommending that counters for non-configured
     connections are not appropriate for accounting purposes
     (Al)

   + Transport Control Traffic --Need to modify objects/text 
     for In/OutCntrlPackets, In/OutCntrlOctets 
     (Peter)

   + Directory Activities -- Need to modify objects/text 
     for Directory Activities objects (Peter)
  
NOTES
-----

1) The participants confirmed agreement to development of a
   common mib for DLSw.

2) The participants agreed to continue work on the DLSw MIB
   as an IETF working group, if possible. The work would
   continue in both AIW & IETF; similar to how MIBs were
   developed for the Frame Relay Service MIB (FR Service MIB
   worked concurrently at IETF and FR Forum by common set
   of participants). A DLSw MIB BOF should be requested for the
   upcoming IETF meeting. The overall goal is to accelerate
   the DLSw MIB group's meeting schedule to produce a high-quality
   an IETF standard MIB.

3) The group agreed that the MIB should support manager entity
   configuration and control of DLSw parameters and functions, in
   addition to monitoring capabilites.

4) The group agreed to the proposed table structure (with changes
   discussed during the meeting) for the first cut of the DLSw MIB.

5)  Scott Barvick of Wellfleet reviewed the structure of
   their enterprise-specific MIB module.

6) Need to add objects that identify the DLSw node global capabilities.
   It would be generally useful to have objects that control
   window size, keep-alives, etc.

7) Agents for DLSw products that do not support NetBIOS should not
   be required to support NetBIOS-specific objects. 
   The MIB should reflect this by defining NetBIOS groups
   in the COMPLIANCE/CONFORMANCE statements.

8) The MIB should allow for defining/monitoring capabilities at different
   levels of granularity. For example, there should be global capabilities, 
   interface level, per-partner, per SAP capabilities.

9) For Connection statistics, it would be useful to know if a connection
   closed due to errors, and if there are traffic problems on that
   connection.

10) The Transport Connection information (p.B-7) should support non-
   standard partners. Consider using a single object that indicates
   whether or not a node supports capabilities exchange (CAPEX).

11) The MIB should contain explorer traffic counts.

12) SNMP Standard MIB Design Practices for SNMPv2 & backward
    compatibility with SNMPv1 (per  D. Kostick)

    o DO NOT use these SNMPv2 syntaxes:
      
      BIT STRING
      Nsap Address
      Counter64
      UInteger32

      .....either directly or through a textual convention..

    o After and SNMPv2 MIB module is completed, it can
      be converted to v1 format by emailing the MIB to:
      [email-masked]. You'll receive the
      SNMPv1 MIB in an email response.

13) The Transport Connection Table should contain information
    that was received via CAPEX from partners. Information that
    the node sent out should be modelled in a different table or
    set. SNA and NetBIOS support objects should be moved to SAP list.

14) Move the objects proposed under the SNA Resources list (p. B.9)
    to the TC Table.

15) Remove Transport Connection Event Table for now.